Skip to content

W-20162376-DR-responsibilities#862

Merged
luanamulesoft merged 16 commits intolatestfrom
W-20162376-DR-responsibility-LDS
Mar 19, 2026
Merged

W-20162376-DR-responsibilities#862
luanamulesoft merged 16 commits intolatestfrom
W-20162376-DR-responsibility-LDS

Conversation

@luanamulesoft
Copy link
Contributor

…CH2 HA/DR

  • Add HA vs DR definitions and RTO/RPO
  • Add Shared Responsibility table (MuleSoft vs Customer) for DR
  • Add Customer Responsibility for Disaster Recovery section
  • Expand Suggested Alternative Deployment Model with GSLB/DLB and health checks
  • Apply style guide: active voice, contractions, no non-acronym parentheses, conciseness

Made-with: Cursor

Writer's Quality Checklist

Before merging your PR, did you:

  • Run spell checker
  • Run link checker to check for broken xrefs
  • Check for orphan files
  • Perform a local build and do a final visual check of your content, including checking for:
    • Broken images
    • Dead links
    • Correct rendering of partials if they are used in your content
    • Formatting issues, such as:
      • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
      • Messed up tables
      • Proper indentation
      • Correct header levels
  • Receive final review and signoff from:
    • Technical SME
    • Product Manager
    • Editor or peer reviewer
    • Reporter, if this content is in response to a reported issue (internal or external feedback)
  • If applicable, verify that the software actually got released

…CH2 HA/DR

- Add HA vs DR definitions and RTO/RPO
- Add Shared Responsibility table (MuleSoft vs Customer) for DR
- Add Customer Responsibility for Disaster Recovery section
- Expand Suggested Alternative Deployment Model with GSLB/DLB and health checks
- Apply style guide: active voice, contractions, no non-acronym parentheses, conciseness

Made-with: Cursor
@luanamulesoft luanamulesoft self-assigned this Mar 13, 2026
@luanamulesoft luanamulesoft requested a review from a team as a code owner March 13, 2026 20:26
@luanamulesoft luanamulesoft changed the title W-20162376: Add CloudHub 1.0 DR shared responsibility and align with … W-20162376-DR-responsibilities Mar 13, 2026
[%header,cols="1a,2a"]
|===
|Party |Responsibility
|MuleSoft |Control plane availability: Anypoint Platform UI, deployment APIs, and platform services within the provisioned region
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think, since some of these are full sentences, they should all have periods.

* Application deployment: Deploy the same or equivalent applications in a backup region and keep them in sync with configuration and code.
* Data and state: Replicate or back up external data stores such as databases, caches, and object stores that your integrations use so applications in a DR region can access the data they need. Anypoint Object Store v1 and v2 are regional; they don't provide cross-region failover.

For guidance on designing HA and DR topologies—including active-active, warm standby, and cold standby—see xref:mule-runtime::hadr-guide.adoc[High Availability and Disaster Recovery].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They say that the use of em-dashes is an indicator that AI wrote it... :)

. Verify that the backup region is serving traffic and that dependent systems use the correct endpoints or data stores.
. When the primary region recovers, optionally fail back by switching traffic from the backup region back to the primary and resyncing data when needed.

Your RTO depends on how quickly you complete these steps and, for cold or warm standby, on how long it takes to start or scale the backup application. For active-active setups, traffic continues on the remaining region without a switch. For more on recovery types and topologies, see xref:mule-runtime::hadr-guide.adoc[High Availability and Disaster Recovery] and xref:cloudhub-2::ch2-ha-dr.adoc[CloudHub 2.0 High Availability and Disaster Recovery].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(You can leave the link text blank to auto-fill with the heading.)

hannanelson
hannanelson previously approved these changes Mar 18, 2026
Co-authored-by: Hanna Nelson <hanna.nelson@mulesoft.com>
luanamulesoft and others added 2 commits March 19, 2026 12:38
Co-authored-by: Hanna Nelson <hanna.nelson@mulesoft.com>
Co-authored-by: Hanna Nelson <hanna.nelson@mulesoft.com>
@terminology-check
Copy link

This PR contains some terms that are considered warnings according to the Inclusive Product Language initiative

  • cloudhub/modules/ROOT/pages/cloudhub-hadr.adoc: man-made
    Please, use other terminology for the found warnings. You can follow the suggested replacements described here.

@luanamulesoft luanamulesoft merged commit 4a40d06 into latest Mar 19, 2026
5 checks passed
@luanamulesoft luanamulesoft deleted the W-20162376-DR-responsibility-LDS branch March 19, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants